This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Oh come on. ~Lorraine Umkiteroopsi 22.Jul.03 06:28 PM a Web browser Notes Client 6.0.2 CF1All Platforms
Get over it.
Notes has been backwardly compatible since about version 2. I routinely run multiple instances of v4.6, v5.10, v6.02 all at the same time.
(for these folks new to this discussion - install SEPARATE executable directories, install SEPARATE data directories, be very careful where notes.ini lives, use "nlnotes" instead of "notes" to run, and use the "=<pathtonotes.ini\notes.ini" parameter on startup. God, I've typed that so often, my fingers didnt need telling).
v6.5 is supposed to be a complete over-the-top-install of v6.x. So thats why its difficult.
The migration path for notes has *always* been (and probably always will be)
Server first
Then clients
then applications.
So if you try and use a later version (significantly later, I hasten to add) to tweak code, then of *course* the design elements are going to start storing more information in them. Thats what we *want* them to do, after all ?
Whats the alternative ? Rip and replace ? Or never have any new features ?
We're supposed to know this stuff - heavens knows, if you read enough of this discussion Db over the years - you would have it drummed into you again and again.
So what that you are not using the newest shiniest development tool against your three year old code servers (and probably even older clients) ?
Notes is meant to only have one code-base on a wintel box -thats cos the file activation stuff, and the registry class stuff isnt smart enough to figure out that more than one version of a single executable program might be able to mess with a particular file-type.
So we, as developers in a multi-version environment, will *always* have to mess around with this. Look on the bright side - there's not a snowball in hells chance of that working with an M$ solution.
not backwardly compatible? No.
I wrote a nasty, server side activation macro last week that locally replicated a notes database, then automatically FTP'd it to the server. I wrote it using my 6.0.2 client, and it works on a v4.6.7 server running NT4.0. So its even forward-compatible if your reasonably careful.
[And a bit more positivity from yourself would avoid such negative responses, methinks]
---* Bill
[Okay, I admit it. I'm cranky today. My usual 800 mile commute preceeded by 3 hours sleep has left me in a less than diplomatic state. Apologies]